Syllabus Information

5.1. Methodological overview

The course learning process is based on:

• Lectures
• Problem-based learning in small group sessions.
• Practical sessions in the laboratory.
• Tutored work at the end of the semester (evaluated independently).
• Voluntary seminars and nonacademic tutorials to complement training activities.
• Effective study of the concepts

5.2. Learning tasks

The learning activities that will help the student to achieve the objectives of the subject are the following ones:

• Development of the subject program in the lectures.
• In the lessons of problems, the concepts discussed in the lectures will be worked on detail.
• In the computer lab sessions small groups of students will work supervised by a teacher.
• Students can also attend personalized tutorial classes.

5.3. Syllabus

The program to be developed in this course is:

• Architecture Processor: Interpretation and translation, machine and assembly language, development environment, representation and coding of information, basic operations, registers and memory, addressing modes, instruction set, translation of data structures and control of high-level languages.
• Subroutines: Procedure calls, activation record. Case study: Integration of high-level language code with assembly code and library routines.
• I/O subsystem: Generic model device driver records. Basic methods of synchronization and transfer. Exceptions. Integration of peripherals in microcontrollers.

5.4. Course planning and calendar

Schedule sessions and presentation of works

The educational organization of the course is as follows.

• Lectures (2 hours per week)
• Problem classes (1 hour weekly)
• Computer lab sessions:
  • Escuela de Ingeniería y Arquitectura de Zaragoza: 2 hours every 2 weeks
  • Escuela Universitaria Politécnica de Teruel: 1 hour a week
• Tutorial and evaluation activities

The timetable of classes and practice sessions will be defined when the academic calendar of the University of Zaragoza is approved.

Student Work

To achieve the targets of this subject, students have to spend about 150 hours distributed as follows:

• 56 hours approximately, during the learning activities (lectures, problems and practical lab sessions)
• 51 hours of personal study (study of notes and texts, problems solving problems, preparation for classes and practices, and learning of the software development process)
• 40 hours of software development work
• 3 hours for the written final exam.

5.5. Bibliography and recommended resources